-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[COMPLIANCE] Add Copyright and License Headers #13103
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
March 13, 2023 20:07
c330d5e
to
a748da7
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
March 20, 2023 16:03
a748da7
to
6fed2ad
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
April 10, 2023 16:03
6fed2ad
to
9b24827
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
April 17, 2023 16:03
9b24827
to
2a75776
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 1, 2023 16:03
2a75776
to
061938a
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 8, 2023 16:03
061938a
to
89054d4
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 15, 2023 16:03
89054d4
to
718e1d1
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 22, 2023 16:03
718e1d1
to
dbaca2b
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 29, 2023 16:03
dbaca2b
to
505f152
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 5, 2023 16:03
505f152
to
0d7b705
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 12, 2023 16:03
0d7b705
to
d37195d
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 19, 2023 16:03
d37195d
to
dde1041
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 26, 2023 16:03
dde1041
to
a7590ab
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 3, 2023 16:03
a7590ab
to
2b7def3
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 17, 2023 16:03
2b7def3
to
4504d05
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 31, 2023 16:04
4504d05
to
65018f3
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there 👋
This PR was auto-generated as part of an internal review of public repositories that are not in compliance with HashiCorp's licensing standards.
Frequently Asked Questions
Why am I getting this PR?
This pull request was created because one or more source code files were found missing copyright and/or license headers.More info is available in the RFC
How do you determine which files should get copyright headers?
Attempts are made to skip scanning autogenerated files (e.g., `go.mod`) and prose. If you find file types you feel should be excluded from future scans, please reach out to:#proj-software-copyright
I have a file or folder which should be exempted, how do I do that?
You may exempt certain files or folders from being scanned by adding a `.copywrite.hcl` config in the root of your repo. You can use the [`copywrite init`](https://go.hashi.co/copywrite) command to interactively create a config for this project.An example schema can be found below. Add a doublestar**-capable pattern to the
header_ignore
list to skip it in future scans.I added a config. How do I trigger this PR to be rebased?
HashiCorp employees can use the [Copywrite SlackBot](https://hashicorp.slack.com/archives/D052WARFFS8) to trigger a rebase. You can DM the slackbot with "headers vagrant" to trigger a PR rebasing.Why don't the headers include a copyright date?
Copyright headers are not required to include a year. In the interest of pragmatism, HashiCorp has decided to exclude the year from headers and instead list it in the LICENSE file at the root of the repository instead.Additional FAQs are available at https://go.hashi.co/header-faq
Please approve and merge this PR in a timely manner to keep this source code compliant with our OSS license agreement. If you have any questions or feedback, reach out to #proj-software-copyright.
Thank you!
Powered by copywrite, made with ❤️ by @hashicorp